Skip to content

ci: Enable floating tags - #1627

Merged
Techassi merged 13 commits into
mainfrom
ci/enable-floating-tags
Sep 3, 2026
Merged

ci: Enable floating tags#1627
Techassi merged 13 commits into
mainfrom
ci/enable-floating-tags

Conversation

@Techassi

@Techassi Techassi commented Sep 2, 2026

Copy link
Copy Markdown
Member

Part of https://github.com/stackabletech/internal-issues/issues/169.

Note

These changes were tested as best as they could here:

It should be noted, that 0.0.0-dev is already considered floating and as such no extra tag is produced. Testing with a version which will produce a second tag will be done later.

This PR wires up floating tag support for all product images. We currently still default to false to make sure everything continues to work as expected (and without changing behaviour).

@Techassi Techassi self-assigned this Sep 2, 2026
@Techassi Techassi moved this to Development: In Progress in Stackable Engineering Sep 2, 2026
@Techassi
Techassi marked this pull request as ready for review September 2, 2026 14:06
@Techassi Techassi moved this from Development: In Progress to Development: Waiting for Review in Stackable Engineering Sep 2, 2026
@dervoeti dervoeti moved this from Development: Waiting for Review to Development: In Review in Stackable Engineering Sep 3, 2026
@dervoeti
dervoeti self-requested a review September 3, 2026 07:56

@dervoeti dervoeti left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Regarding the defaults job, would something like this work maybe?

      with:
        product-name: krb5
        sdp-version: ${{ case(github.ref_type == 'tag', github.ref_name, '0.0.0-dev') }}
        registry-namespace: sdp
        # Keep these defaults in sync with the workflow_dispatch input defaults above.
        publish: ${{ github.event_name != 'workflow_dispatch' || inputs.publish }}
        floating-tag: ${{ github.event_name == 'workflow_dispatch' && inputs.floating-tag }}

Would shorten the whole code quite a bit.

@dervoeti dervoeti left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, just one optional suggestion to make the code more compact.

@Techassi

Techassi commented Sep 3, 2026

Copy link
Copy Markdown
Member Author

Regarding the defaults job, would something like this work maybe?

I honestly don't know, because empty values behave very weirdly in GHA. They only sometimes become a faulty value. This definitely would need a round of testing.

I'm happy to explore this option, but would prefer to do so in a separate PR.

@Techassi
Techassi added this pull request to the merge queue Sep 3, 2026
Merged via the queue into main with commit 9ee33bf Sep 3, 2026
3 checks passed
@Techassi
Techassi deleted the ci/enable-floating-tags branch September 3, 2026 11:42
@Techassi Techassi moved this from Development: In Review to Development: Done in Stackable Engineering Sep 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Development: Done

Development

Successfully merging this pull request may close these issues.

2 participants